feat(#216): multiple bt adapter support#267
Merged
cachebag merged 3 commits intodevelopmentfrom Mar 27, 2026
Merged
Conversation
cachebag
added
feature
github-actions
bot
force-pushed
the
bt-adapters
branch
2 times, most recently
from
ebdc78a to
a4d1eb9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #216
Right now,
list_bluetooth_devicespassesNonetopopulate_bluez_info, meaning it always queries BlueZ viahci0. If a device is paired throughhci1, the BlueZ lookup will silently miss it and return (None,None) for name/alias. To fix that properly we'd need to query BlueZ for which adapter owns each device. This involved a bigger change involving the BlueZorg.bluez.Adapter1interface.